What I did

Added support for classic prev/next pagination to useResourceList, alongside the existing infinite scroll mode. The new paginationType prop controls which mode is used — "infinite" remains the default, so there are no breaking changes.

Changes

• Added paginationType?: "infinite" | "pagination" to UseResourceListConfig
• Renamed infiniteFetcher → listFetcher (supports both modes internally)
• Added PaginationInfo component with prev/next buttons, page range display, and scroll-to-top on page change
• useResourceList returns a Pagination component when paginationType: "pagination" is set (type-safe via function overloads)
• useResourceFilters → FilteredList forwards paginationType automatically
• Pagination mode is restricted to Core API (not Metrics API)

Usage examples

Basic pagination:

const { ResourceList, Pagination } = useResourceList({
  type: 'orders',
  paginationType: 'pagination',
})

return (
  <>
    <ResourceList ItemTemplate={OrderTemplate} />
    <Pagination />
  </>
)

Via FilteredList (from useResourceFilters):

<FilteredList
  type="orders"
  paginationType="pagination"
  ItemTemplate={OrderTemplate}
/>

Default (infinite scroll, unchanged):

const { ResourceList } = useResourceList({ type: 'orders' })

How to test

1. Use the WithPagination or WithPaginationAsTable Storybook stories under Resources / useResourceList
2. Verify prev/next buttons are disabled while loading and on first/last page
3. Verify page range label updates correctly (e.g. 1–25 of 312)
4. Verify infinite scroll still works when paginationType is omitted

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests).
• Make sure to add/update documentation regarding your changes.
• You are NOT deprecating/removing a feature.